Hello everyone,

 

I am installing VMWare workstation version 10.0.3 and 11 as well on WIndows 8.1.

There is an error when i installed it. The error is KERNEL_SECURITY_CHECK_FAILURE. It stopped my laptop. and return BSOD.

Any solutions to continue on it

 

run this command to enable Windows Installer Service in safe mode

REG ADD "HKLM\SYSTEM\CurrentControlSet\Control\SafeBoot\Network\MSIServer" /VE /T REG_SZ /F /D "Service"

then start Windows Installer Service by tryping this command

net start msiserver

uninstall VMWare workstation version 10.0.3 and 11, and remove all physical network adapter from Device Manager

Boot in normal mode and try to install again

If not working please provide the dump file to investigate more

• Edited by britishdhez 3 hours 4 minutes ago

run this command to enable Windows Installer Service in safe mode

REG ADD "HKLM\SYSTEM\CurrentControlSet\Control\SafeBoot\Network\MSIServer" /VE /T REG_SZ /F /D "Service"

then start Windows Installer Service by tryping this command

net start msiserver

uninstall VMWare workstation version 10.0.3 and 11, and remove all physical network adapter from Device Manager

Boot in normal mode and try to install again

If not working please provide the dump file to investigate more

• Edited by britishdhez Wednesday, March 11, 2015 4:15 AM

I is not still working.

my dump file as below:

Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\031115-99484-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path.           *
* Use .symfix to have the debugger choose a symbol path.                   *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is: 
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17668.amd64fre.winblue_r8.150127-1500
Machine Name:
Kernel base = 0xfffff800`4e68f000 PsLoadedModuleList = 0xfffff800`4e968250
Debug session time: Wed Mar 11 20:50:38.236 2015 (UTC + 7:00)
System Uptime: 0 days 0:06:00.894
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.................................................
Loading User Symbols
Loading unloaded module list
..........

************* Symbol Loading Error Summary **************
Module name            Error
ntoskrnl               The system cannot find the file specified

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 139, {3, ffffd0002202b1b0, ffffd0002202b108, 0}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
Probably caused by : ndis.sys ( ndis+303b1 )

Followup: MachineOwner
---------

normally ndis.sys caused by 3rd party antivirus or firewall software causing NETBIOS conflicts and also old network adapter driver, that why my suggestion above is going to safe mode and remove network card related, it will isolate 3rd party software issue

I suggest you remove your antivirus first to test, and also update all network card driver (you can find it at PC manufactured site or MB manufactured site if you built in your PC)

If other than installation VMware workstation PC is working fine, I suggest you also contact VMware support to investigate more since we have limitation regarding product knowledge here

Let us know the update

• Edited by britishdhez 4 hours 21 minutes ago
• Proposed as answer by Karen HuMicrosoft contingent staff, Moderator 2 minutes ago

normally ndis.sys caused by 3rd party antivirus or firewall software causing NETBIOS conflicts and also old network adapter driver, that why my suggestion above is going to safe mode and remove network card related, it will isolate 3rd party software issue

I suggest you remove your antivirus first to test, and also update all network card driver (you can find it at PC manufactured site or MB manufactured site if you built in your PC)

If other than installation VMware workstation PC is working fine, I suggest you also contact VMware support to investigate more since we have limitation regarding product knowledge here

Let us know the update

• Edited by britishdhez Thursday, March 12, 2015 2:56 AM
• Proposed as answer by Karen HuMicrosoft contingent staff, Moderator Thursday, March 12, 2015 7:15 AM
• Marked as answer by Karen HuMicrosoft contingent staff, Moderator 5 hours 49 minutes ago

normally ndis.sys caused by 3rd party antivirus or firewall software causing NETBIOS conflicts and also old network adapter driver, that why my suggestion above is going to safe mode and remove network card related, it will isolate 3rd party software issue

I suggest you remove your antivirus first to test, and also update all network card driver (you can find it at PC manufactured site or MB manufactured site if you built in your PC)

If other than installation VMware workstation PC is working fine, I suggest you also contact VMware support to investigate more since we have limitation regarding product knowledge here

Let us know the update

• Edited by britishdhez Thursday, March 12, 2015 2:56 AM
• Proposed as answer by Karen HuMicrosoft contingent staff, Moderator Thursday, March 12, 2015 7:15 AM
• Marked as answer by Karen HuMicrosoft contingent staff, Moderator Friday, March 13, 2015 1:27 AM

Can you provide a dump file(s) via a public folder on OneDrive or similar site?

Here's a couple of links on using OneDrive (SkyDrive):

http://windows.microsoft.com/en-ca/skydrive/add-photos-files-faq

http://windows.microsoft.com/en-ca/onedrive/share-file-folder

I boot my laptop in safemode and remove network cards. then i reinstalled VMWare, it was successful

Thank for your useful helping

• Marked as answer by Karen HuMicrosoft contingent staff, Moderator 5 hours 49 minutes ago

I boot my laptop in safemode and remove network cards. then i reinstalled VMWare, it was successful

Thank for your useful helping

• Marked as answer by Karen HuMicrosoft contingent staff, Moderator Friday, March 13, 2015 1:27 AM

glad it help

• Edited by britishdhez 5 hours 52 minutes ago

glad it help

• Edited by britishdhez Friday, March 13, 2015 1:24 AM